ShowTable of Contents
As part of this article, it is assumed that the Sametime 8.5.1 Embedded Client has already been installed into your Lotus Notes 8.5.1 Client that has had Fixpack 4 applied as per the Sametime Documentation recommended system requirements. (Lotus Notes 8.5.1 & 8.5.2 do NOT ship with the Embedded Sametime 8.5.x client – they ship with the 8.0.2 Sametime embedded client)
Cisco Phone Control and Presence 8.0 Plug-in
You will need to obtain the Cisco Phone Control and Presence 8.0 with IBM Lotus Sametime Plug-In which is available from Cisco. For this article I will assume that you have access to the download.
Here is a link to the Integration Note for the Deploying of the Cisco Phone Control and Presence 8.0 with IBM Lotus Sametime:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucibmlotus/cpcap/8x/english/integration/guide/cpcapig.html#wp64653
Follow the instructions in this document for the configuring of the update site.
However, when you read the section:
2. How to Set Up the Plug-in Update Site, there is a Note that states:
If Cisco Unified Messaging with IBM Lotus Sametime is also being deployed, copy all the .jar files from the UpdateSite/plugins and UpdateSite/features directories of that package to the respective directories in this package. This creates a combined update site so that the plug-ins can be configured together.
What I have learnt from previous implementations is DO NOT DO THIS as it does not work. If you have a combined Update Site, then the Unified Messaging Plug-In, will not install and constantly errors. You must create separate Update Sites.
Cisco Unified Messaging 8.0 Plug-In
You will need to obtain the Cisco Unified Messaging 8.0 with IBM Lotus Sametime Plug-In which is available from Cisco. For this article I will assume that you have access to the download.
Here is a link to the Release Notes for Cisco Unified Messaging 8.0 with IBM Lotus Sametime:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucibmlotus/unifiedmsg/8x/release/notes/801cumstrn.html
Follow the instructions in this document for the configuring of the update site.
Create an Eclipse Update Site
If you already have Eclipse update site in your Domino environment, you can skip this step.
The easiest way to create an Eclipse Update Site is to use Notes 8.x Eclipse Update Site template.
Go to File ð Application ð New, enter the required data, and check the Show advanced templates check-box. Be sure you selected your server for template list. Select the Eclipse update site and click OK. When the process finishes, you will have your eclipse update site.
Create a Widget catalog database
Again, if you already have a widget catalog database in your Domino environment, you do not need to read this.
The easiest was to create a Widget Catalog is to use Notes 8.x Widget Catalog template.
Go to File ð Application ð New, enter the required data, and check the Show advanced templates check-box. Be sure you selected your server for template list. Select the Widget Catalog and click OK.
When the process finishes, you will have your widget catalog.
Importing the Plug-In Update Site
Now that you have your locally saved, configured plug-in updatesite files along with your eclipse update site and widget catalog on your Domino server, you can proceed with deployment.
What you need to do now is to import your plug-in to your eclipse update site database. This is a simple step.
Open your Eclipse Update Site database and click on the Import local update site action button. A dialog pops up. All you need to do is to point the location of the updatesite folder of the configured plug-in and select the site.xml file on your hard drive and select OK. If all goes well, you should have an update site imported in about a minute or so.
You will need to repeat this process for each update site that you want to import.
You should see something like this:

Creating a widget for your plug-in
To deploy a plug-in for the integrated Lotus Notes with embedded Sametime client, you need to create a widget from your update site.
You will have to manually create your own extension.xml file that you will attach to the Widget. It was my experience that attempting to use the “wizards” does NOT generate a correctly formed extension.xml file whereas manually created ones work.
You can name the file whatever you want, as long as it has the correct format. Below is the content of my extension file used for the Cisco Phone Control and Presence Plug-In (attributes marked bold are changeable).
<?xml version="1.0" encoding="UTF-8"?>
<webcontextConfiguration version="1.1">
<palleteItem id="com.cisco.sametime.phone.featurest800" imageUrl=""
providerId="com.ibm.rcp.toolbox.prov.provider.ToolboxProvisioning"
title="Cisco Phone Control and Presence"
url="nrpc://myupdatesiteserver.com/__482577b9000551b5/site.xml">
<preferences>
</preferences>
<data>
<installManifest>
<![CDATA[
<install>
<installfeature description="Cisco Phone Control and Presence"
id="com.cisco.sametime.phone.featurest800"
name="Cisco Phone Control and Presence"
required="true">
<requirements>
<feature id="com.cisco.sametime.phone.featurest800" version="8.0.1.1094"/>
</requirements>
</installfeature>
</install>
]]>
</installManifest>
</data>
</palleteItem>
</webcontextConfiguration>